Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Revert PR #1156 "Make DTLS fragment stay within MTU size range" because it causes a memory leak #1342

Merged
merged 4 commits into from
Feb 21, 2024

Conversation

ibc
Copy link
Member

@ibc ibc commented Feb 21, 2024

Details

As perfectly documented in issue #1340, there is a leak due to the usage of BIO_set_callback_ex() whose fix is unclear and, anyway, I'm pretty sure that the usage of that OpenSSL utility makes the performance worse.

As a workaround for issue #1100 (which now must be reopened), in order to avoid "DTLS fragment exceeds MTU size if the certificate is large", users should not pass a big DTLS certificate to mediasoup.

…se it causes a memory leak

- Fixes #1340
- Reopents #1100

### Details

As perfectly documented in issue #1340, there is a leak due to the usage of `BIO_set_callback_ex()` whose fix is unclear and, anyway, I'm pretty sure that the usage of that OpenSSL utility makes the performance worse.

As a workaround for issue #1100 (which now must be reopened), in order to avoid "DTLS fragment exceeds MTU size if the certificate is large", users should not pass a big DTLS certificate to mediasoup.
@ibc ibc merged commit af2ae37 into v3 Feb 21, 2024
23 checks passed
@ibc ibc deleted the revert-pr-1156-make-dtls-fragment-stay-within-mtu-size branch February 21, 2024 17:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants